Auxiliary Channel Remote Device Management, Diagnostics, and Self-Installation

ABSTRACT

A remote device management, diagnostics, and self-installation architecture employs multiple wireless links, which may include a local wireless link and a remote wireless link. The architecture employs cellular channels for remote management of customer premises equipment (CPE). Within the architecture, test devices may operate on the CPE. As examples, the test devices may include a cellular radio, or the test devices may be in communication with another device that includes the cellular radio.

PRIORITY CLAIM

This application claims priority to provisional application Ser. No.61/904,878, filed Nov. 15, 2013, which is entirely incorporated byreference.

TECHNICAL FIELD

This disclosure relates to management, diagnostics, andself-installation of devices at locations that are remote from anoperations center for a service provider.

BACKGROUND

Rapid advances in electronics and communication technologies, driven byimmense customer demand, have resulted in the widespread adoption of anextremely broad array of electronic devices in every aspect of society.For example, some estimates put the number of subscriber connections forcellular phones in use around the world at nearly 80% of the world'spopulation. As another example, broadband Internet access is commonlyavailable in the home, and provisioned with customer premises equipmentsuch as DSL and cable modems, wireless routers, and network devices suchas switches and hubs. It can be quite costly for a service provider toperform a service call and send a technician to the customer site fortroubleshooting.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example network diagram.

FIG. 2 shows an example management system.

FIG. 3 shows an example of logic that may be executed at the managementsystem.

FIG. 4 shows an example of a diagnostic device.

FIG. 5 shows an example of logic that may be executed by the diagnosticdevice.

FIG. 6 shows additional examples of network diagrams.

FIG. 7 shows another example of a network diagram.

FIG. 8 shows another example of a network diagram.

DETAILED DESCRIPTION

FIG. 1 shows an example network 100 that shows a management system 102in communication with a service location 104. The network 100 is one ofmany possible examples of architectures applicable to the managementtechniques discussed below. The network 100 connects the managementsystem 102 to the service location 104 through one or more intermediatenetworks 106. In the path toward the service location 104 there may be,for example, a central office 108, and an access network 110.

As just one example, the management system 102 may be a facilityassociated with a network operator who provides any combination ofservices to customers, such as voice services, Internet (or other data)services, and phone services. The management system 102 may connectthrough the networks 106 to a central office 108. The central office 108in turn connects to the service location 104 through access networks 110which may include phone lines (e.g., for DSL Internet service), cablelines (e.g., for Cable Internet service), Radio Frequency (RF),Satellite, microwave, or other links. The service location 104 may be ahome, a business, a government location, or other location that obtainsservices from the network operator.

At the management system 102, technicians 112 may be employed to help anindividual 114 present at the service location 104 (e.g., a customer intheir home) troubleshoot equipment at the service location 104. Themanagement system 102 may be local or remote with respect to the servicelocation 104. Further, while the management system 102 may be associatedwith the network operator, other third party management systems may alsoprovide the same or similar functionality. For example, the manufacturerof a DVR or any other type of device may operate its own managementsystem, and provide a configuration or maintenance service to purchasersof its devices. Regardless of the location of the management system 102,or the entity operating the management system 102, it may beeconomically costly to perform a service call to send a technician tothe service location 104 to assist with troubleshooting. The techniquesdescribed below help avoid the cost of a service call, and have otheradvantages as well.

At the service location 104 there may be many different types ofequipment 116, any of which may be subject to management actions by themanagement system 102. The management actions may include actions suchas troubleshooting, configuration, and software and firmware upgrades,as examples. Continuing the example of the network operator, the servicelocation 104 may include equipment such as a network interface device118 (e.g., a DSL modem or cable modem), a wireless router 120, and anetwork switch 122. Additional examples of equipment include thecomputers 124, printers 126, displays 128, network attached storage(NAS) 130, scanners 132, and game systems 134 connected to the networkeither wirelessly or in a wired manner, e.g., via Ethernet.

At the service location 104, the individual 114 interacts with adiagnostic device 136. The diagnostic device 136 may run a diagnosticapplication 138. As one example, the diagnostic device 136 may be asmartphone with multiple communication interfaces. The diagnostic device136 may, for example, communicate over a first wireless link 140, insome instances referred to below for clarity as a wireless diagnosticlink. The first wireless link 140 may be, as examples, a cellulartelephony link (e.g., a GSM, 2G, 3G, or 4G/LTE link) or a Voice overInternet Protocol (VoIP) link to a cellular base station 141 that isalso in communication with the management system 102. The diagnosticdevice 136 may also communicate with any of the equipment at the servicelocation 104 using a second wireless connection 142, in some instancesreferred to below for clarity as a wireless analysis link. As examples,the second wireless connection 142 may be a Bluetooth™ connection, aNear Field Communications (NFC) connection, a wireless network (WiFi)connection, a WiFi direct link, or another type of wireless connection.

The second wireless connection may be a local link in the sense that itexists between the diagnostic device 136 and a particular piece ofequipment in the service location 104. The first wireless link may be aremote link in the sense that it connects the diagnostic device 136 tothe possibly more distant management system 102. For the purposes ofdiscussion below, the first wireless link (e.g., a cellular telephonylink) is referred to as a wireless “diagnostic” link. The secondwireless link (e.g., a Bluetooth™ link) is referred to as a wireless“analysis” link.

In that regard, the wireless diagnostic link may transmit and receive,as examples, management commands 144, management data 146, andmanagement instructions 148. The management commands 144 may, as a fewexamples, instruct the diagnostic device 136 to connect to a piece ofequipment, run a test on the equipment, gather data from the equipment,install firmware on the equipment, or set configuration settings on theequipment. The management data 146 may provide the configurationsettings, the firmware, or specify data for the tests, as examples tothe diagnostic device 136 and the equipment 116. The management data 146going back to the management system 102 may include, the test results,configuration parameters, current firmware version, video or audiocaptured by the diagnostic device (e.g., through an onboard camera andmicrophone), and other data characteristic of the Device Under Test(DUT) that the diagnostic device 136 may sense, or that the DUT mayreport, e.g., temperature, fan speed, up-time, OS or other softwareversion, service performance data (e.g., data rate, error rate, latency,jitter, and the like) port status, model number, serial number, linkstatus, memory configuration, and other equipment characteristics. Themanagement instructions 148 may specify operations for the individual114 to perform, such as install or run the diagnostic application 138,bring the diagnostic device within local wireless range of the DUT, orperform specified actions on the equipment, as examples.

The wireless diagnostic link may also push a diagnostic application 150to the diagnostic device 136. In that respect, the management system 102may cause transmission of the diagnostic application 150 over the firstwireless link 140 to the diagnostic device 136 (e.g., to a smartphone).The management system 102 may also instruct the diagnostic device 136 toinstall and execute the diagnostic application.

As one example, the wireless analysis link may operate according toAndroid™ operating system (OS) NFC technologies such as Android Beam orS-Beam. The diagnostic device 136 may thereby, for example, use NFC toinitiate Bluetooth™ operation on the equipment and the diagnostic device136, pair them, perform management actions, and disable the Bluetooth™link once the management actions are complete.

One use case is that the individual 114 detects, for example, a networkfault and calls the management system 102 for their network operator,e.g., on the individual's smart phone, thereby establishing thediagnostic link. On the call, the technician 112 attempts to manage thenetwork interface device 118 using the access network 110. If thetechnician 112 is unsuccessful, then the technician 112 may push thediagnostic application 150 to the smartphone. The technician 112 maythen instruct the individual 114, e.g., via the voice connection, orthrough instructions delivered through the diagnostic application 150,to stand within Bluetooth™ range of the network interface device 118.The smartphone and the network interface device 118 establish aBluetooth™ link as the analysis link. Once established, the technician112 may instruct the diagnostic application 150 and the individual 114to execute management actions on the network interface device 118 to,e.g., find and correct network configuration faults and restore Internetservice.

FIG. 2 shows an example management system 200, which illustrates onepossible architecture for the management system 102 in FIG. 1. Themanagement system 200 includes a communication interface 202, diagnosticlogic 204, and a user interface 206. The communication interface 202 mayinclude one or more Ethernet ports, cellular telephony interface, or anyother type of wired or wireless communication interface for performingthe communications described above with respect to FIG. 1. Thecommunication interface 202 sends and receives, e.g., the managementcommands 144, management data 146, as well as management instructions148 and the diagnostic application 150.

The user interface 206 may display, for example, a graphical userinterface (GUI) 210. The user interface 206 may process any of themanagement commands 144, management data 146, and managementinstructions 148, or any other data, and display through the GUI 210 anytype of equipment management interface 212, such as a troubleshootinginterface, configuration interface, or upgrade interface. The equipmentmanagement interface 212 may visualize, as just a few examples,configuration settings, port activity and status, software versions,port parameters, or any other data concerning the DUT. The equipmentdata drives the visualization, analysis, and management of theequipment, which the diagnostic logic 204 may carry out. The user inputs214 provide keyboard, mouse, voice recognition, touchscreen, and anyother type of input mechanisms for technician interaction with themanagement system 200.

The diagnostic logic 204 may be implemented in hardware, software, orboth. In one implementation, the diagnostic logic 204 includes one ormore processors 216 and memories 218. The memory 218 may storediagnostic instructions 220 (e.g., program instructions) for executionby the processor 216. The diagnostic instructions 220 may carry outequipment management using the local and remote wireless links. Thediagnostic instructions 220 may generate the GUI 210. The diagnosticinstructions 220 may also receive diagnostic input from the GUI 210 andin response generate and send or receive diagnostic commands 224,diagnostic data 226, diagnostic information 228, and diagnosticapplications 230 to and from the diagnostic device 136. The managementsystem 102 may store a library of diagnostic applications, any of whichit may push to the diagnostic device 136 and that is suitable forparticular types of equipment (e.g., a DSL modem diagnostic app, and acolor laser printer diagnostic app), types of problems encountered(e.g., loss of Internet connectivity, or inability to connect to awireless router), or types of management actions to perform (e.g., toupgrade firmware, or run periodic maintenance checks).

In other implementations, the diagnostic instructions 220 implement anautomated response system. That is, it is not necessary for a livetechnician 112 to be available to assist the individual 114. As oneexample, the automated response system may include a voice recognitionsystem that facilitates voice driven troubleshooting with the individual114. In other implementations, the diagnostic instructions 220 mayimplement interactive touch-tone menu functionality for troubleshooting,optionally including Interactive Voice Response (IVR) functionality.

FIG. 3 shows an example of logic 300 that may be executed at themanagement system 102, e.g., as the diagnostic instructions 220. Thelogic 300 includes establishing a wireless diagnostic link to adiagnostic device (302). The wireless diagnostic link may be a cellulartelephony link, for example, over which an individual 114 maycommunicate with a technician 112. When the individual 114 has adiagnostic device 136 available, the logic 300 may determine whether adiagnostic application is available for handling the issue at hand(312). If so, the logic 300 may make available a diagnostic application138 to the diagnostic device 136 (314). For example, the logic 300 mayautomatically push the diagnostic application 138 to the diagnosticdevice 136, may provide instructions to the individual 114 fordownloading the diagnostic application 138, or may otherwise make thediagnostic application 138 available to the individual 114.

The logic 300 may then communicate a wireless analysis linkestablishment command over the wireless diagnostic link to thediagnostic device (304). The command may be configured for execution bythe diagnostic application 138, for example. Alternatively, the commandmay be one that that the individual 114 can perform using the existingcapability of the diagnostic device 136, such as creating a Bluetoothlink to the DUT. The logic 300 also receives, over the wirelessdiagnostic link, from the diagnostic device,wireless-analysis-link-obtained diagnostic information concerningequipment at the service location (306). In other words, the managementsystem 102 receives information about the DUT that the diagnostic device136 has obtained through the local wireless analysis link (e.g., theBluetooth link to the equipment).

Responsive to the wireless-analysis-link-obtained diagnosticinformation, the logic 300 may select a management command (308). Themanagement command may, as one example, be a troubleshooting actiondetermined by analysis of the diagnostic information in comparison withor with reference to equipment troubleshooting information. Themanagement system 102 may maintain a database of equipmenttroubleshooting information specific to any particular equipment thatthe management system 102 handles. The logic also communicates themanagement command, data, and instructions over the wireless diagnosticlink to the diagnostic device 136 at the service location (310). Themanagement action may be, for example, instructions to the individual114 to perform, may be actions for the diagnostic application 138 toperform, may be actions for the equipment to perform, or may be anaction for another entity to perform.

The logic 300 may continue to execute management actions until aparticular management goal is resolved (316). The logic 300 may alsodetermine to end the management activity at any time (318). In addition,the logic 300 may perform as many different management actions asdesired (320), for example, troubleshooting an Internet connectivityproblem, then upgrading DSL modem firmware, then resetting the DSLmodem, and then confirming proper Internet connectivity when the DSLmodem restarts. When the logic 300 has not further actions to perform,it may send the diagnostic device an instruction to terminate thewireless analysis link, and may also terminate the wireless diagnosticlink (322).

FIG. 4 shows an example of a diagnostic device 400. The diagnosticdevice 400 is a smartphone in this example, but the diagnostic devicemay be any electronic device capable of establishing a local wirelessconnection to DUT. The diagnostic device 400 may support one or moreSubscriber Identity Modules (SIMs), such as the SIM1 402 and the SIM2404. Electrical and physical interfaces 406 and 408 connect SIM1 402 andSIM2 404 to the rest of the user equipment hardware, for example,through the system bus 410.

The diagnostic device 400 includes a communication interface 412, systemlogic 414, and a user interface 418. The system logic 414 may includeany combination of hardware, software, firmware, or other logic. Thesystem logic 414 may be implemented, for example, in a system on a chip(SoC), application specific integrated circuit (ASIC), or othercircuitry. The system logic 414 is part of the implementation of anydesired functionality in the diagnostic device 400. In that regard, thesystem logic 414 may include logic that facilitates, as examples,running applications; accepting user inputs; saving and retrievingapplication data; establishing, maintaining, and terminating cellularphone calls or data connections for, as one example, Internetconnectivity; establishing, maintaining, and terminating wirelessnetwork connections, Bluetooth connections, or other connections; anddisplaying relevant information on the user interface 418. The userinterface 418 may include a graphical user interface, touch sensitivedisplay, voice or facial recognition inputs, buttons, switches, speakersand other user interface elements.

In the communication interface 412, Radio Frequency (RF) transmit (Tx)and receive (Rx) transceivers 430 handle transmission and reception ofsignals through the antenna(s) 432. The communication interface 412 mayinclude one or more transceivers. The transceivers may be wirelesstransceivers that include modulation/demodulation circuitry, digital toanalog converters (DACs), shaping tables, analog to digital converters(ADCs), filters, waveform shapers, filters, pre-amplifiers, poweramplifiers and/or other logic for transmitting and receiving through oneor more antennas, or (for some devices) through a physical (e.g.,wireline) medium.

As one implementation example, the communication interface 412 andsystem logic 414 may include a BCM2091 EDGE/HSPA Multi-Mode, Multi-BandCellular Transceiver and a BCM59056 advanced power management unit(PMU), controlled by a BCM28150 HSPA+ system-on-a-chip (SoC) basebandsmartphone processer or a BCM25331 Athena™ baseband processor. Thesedevices or other similar system solutions may be extended as describedbelow to provide the additional functionality described below. Theseintegrated circuits, as well as other hardware and softwareimplementation options for the diagnostic device 400, are available fromBroadcom Corporation of Irvine, Calif.

The transmitted and received signals may adhere to any of a diversearray of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or256-QAM), frequency channels, bit rates, and encodings. As one specificexample, the communication interface 412 may include transceivers thatsupport transmission and reception under the 4G/Long Term Evolution(LTE), Bluetooth, and NFC standards. The techniques described below,however, are applicable to other communications technologies.Accordingly, the transceivers 430 may include transceivers for the 3rdGeneration Partnership Project (3GPP), GSM (R) Association, Bluetoothlow energy, WiFi direct, 802.11 a/b/g/n/ac, Wireless Gigabit (WiGig),InfraRed (IR), audio (e.g., ultrasonic), Universal MobileTelecommunications System (UMTS), High Speed Packet Access (HSPA)+, orother communications technologies, partnerships, or standards bodies.

The system logic 414 may include one or more processors 416 and memories420. The memory 420 stores, for example, control instructions 422 thatthe processor 416 executes to carry out any of the processingfunctionality, working in communication with the circuitry in thecommunication interface 412. For example, the control instructions 422may include a diagnostic application 138 received from the managementsystem 102 or any other source.

The control parameters 424 provide and specify configuration andoperating options for the control instructions 422. The memory 420 mayalso store diagnostic information 426 obtained from the DUT. Note thatthe diagnostic information 426 may come over the wireless analysis link142, e.g., transmitted to the diagnostic device 400 by the DUT. Inaddition, the diagnostic information 426 may come from other inputs 428to the diagnostic device 400. Examples of such inputs 428 includemicrophones, video and still image cameras, temperature sensors,vibration sensors, headset and microphone input/output jacks, UniversalSerial Bus (USB) connectors, memory card slots, radiation sensors (e.g.,IR sensors), and other types of inputs.

FIG. 5 shows an example of logic 500 that may be executed by thediagnostic device, e.g., by the control instructions 422. The logic 500includes establishing a wireless diagnostic link to a management system(502). The wireless diagnostic link may be a VoIP link, for example,that an individual 114 may use to explain an equipment problem or ask anequipment question to a technician 112.

When there is a diagnostic application available for the particularissue at hand (504), the logic 500 may automatically receive and installthe diagnostic application 138 on the diagnostic device 136 (506).Alternatively, the logic 500 may receive instructions provided to theindividual 114 for downloading and installing the diagnostic application138.

The logic 500 receives a wireless analysis link establishment commandover the wireless diagnostic link to the management system 102, andestablishes the wireless analysis link (508). The command may be aBluetooth link command, a WiFi direct link command, or other commandthat establishes a wireless link between the diagnostic device and theequipment at the service location 104. The command may be configured forexecution by the diagnostic application 138 or may be an instruction ordirection to the individual 114 for establishing the link through thediagnostic application or by using existing capabilities of thediagnostic device 136.

The logic 500 also receives, over the wireless analysis link, from theequipment, wireless-analysis-link-obtained diagnostic informationconcerning the equipment at the service location (510). In other words,the diagnostic device 136 receives information about the DUT through thelocal wireless analysis link (e.g., the WiFi Direct link to theequipment). In addition, the diagnostic device 136 may receiveadditional diagnostic information through the inputs 428, for example,to obtain a picture or a video of the equipment (512).

The logic 500 sends the diagnostic information to the management system102 (514). In response, the logic 500 may receive a management command,data, and instructions from the management system 102 (516). Themanagement command may be any direction to the individual 114 or thediagnostic application 138. As just a few examples, the managementcommand may be to read configuration settings, to obtain device status,or to read firmware version information. The logic 500 executes themanagement command (518).

The logic 500 may continue to execute management commands until aparticular management goal is resolved (520). The logic 500 may alsodetermine to end the management activity at any time (522). In addition,the logic 300 may perform as many different management actions asdesired (524). When the logic 500 has no further actions to perform, itmay terminate the wireless analysis link, and may also terminate thewireless diagnostic link (526).

The system described above may have certain technical advantages,including leveraging low cost (e.g., Bluetooth) technologies, with thesophisticated, ubiquitous, consumer-friendly, and highly functionalsmart phone/cellular network to provide low-cost and powerful managementconnectivity. The techniques facilitate network operators to transfermany fault isolation and service restoration tasks to the individual114, thus reducing the number of service calls, and otherwise loweringoperational expenses. Further, the management system 102 may centralizemanuals, instructional videos, software updates, and other managementdata in web-based repositories. This may reduce costs for equipmentsuppliers and network operators and simplify use by end customers. Notethat the system described above may provide management connectivity todevices or systems that do not otherwise have fixed-line or short rangewireless management connectivity. Examples include, but are not limitedto, vehicles, power-grid elements, commercial equipment, or any otherequipment not on a fixed-line network. Further, the system usessmartphone resources, such as cameras, to obtain diagnostic data andprovide very flexible management functionality.

The methods, devices, and logic described above may be implemented inmany different ways in many different combinations of hardware, softwareor both hardware and software. For example, all or parts of the systemmay include circuitry in a controller, a microprocessor, or anapplication specific integrated circuit (ASIC), or may be implementedwith discrete logic or components, or a combination of other types ofanalog or digital circuitry, combined on a single integrated circuit ordistributed among multiple integrated circuits. All or part of the logicdescribed above may be implemented as instructions for execution by aprocessor, controller, or other processing device and may be stored in atangible or non-transitory machine-readable or computer-readable mediumsuch as flash memory, random access memory (RAM) or read only memory(ROM), erasable programmable read only memory (EPROM) or othermachine-readable medium such as a compact disc read only memory (CDROM),or magnetic or optical disk. Thus, a product, such as a computer programproduct, may include a storage medium and computer readable instructionsstored on the medium, which when executed in an endpoint, computersystem, or other device, cause the device to perform operationsaccording to any of the description above.

The processing capability of the system may be distributed amongmultiple system components, such as among multiple processors andmemories, optionally including multiple distributed processing systems.Parameters, databases, and other data structures may be separatelystored and managed, may be incorporated into a single memory ordatabase, may be logically and physically organized in many differentways, and may implemented in many ways, including data structures suchas linked lists, hash tables, or implicit storage mechanisms. Programsmay be parts (e.g., subroutines) of a single program, separate programs,distributed across several memories and processors, or implemented inmany different ways, such as in a library, such as a shared library(e.g., a dynamic link library (DLL)). The DLL, for example, may storecode that performs any of the system processing described above.

Various implementations have been specifically described. However, manyother implementations are also possible. For instance, the equipment 116may take many different forms. As examples, the equipment 116 may be anydevice equipped with a wireless transceiver (e.g., Bluetooth or WiFi) orwired interface (e.g., USB or a proprietary cabled interface), includinga home stereo, television, refrigerator, microwave, exercise machine,washer or dryer, or home security system. As additional examples, theequipment may be an engine controller or diagnostic system in a vehicle,a portable gaming device, an entertainment system in the vehicle, or aclimate control system in the home or in the car. Further examples ofthe equipment include industrial machinery such as robots, assemblylines, welders, drill presses, stamping machines, cutting machines, andthe like.

The management instructions 148 may include pictures, diagrams, andvideos that the diagnostic application 138 may display to assist theindividual 114 in managing the equipment. The diagnostic application 138may be provided in multiple languages, selectable by the individual 114.The diagnostic application 138 may implement security and authenticationmechanisms. One example of such mechanisms include instructing thediagnostic device 136 camera to monitor the LED status indicators on theequipment, detecting a specific pattern of response in the LEDs whichhas been initiated via the wireless analysis link 142, and determiningif the detected LED response is consistent with the expected responsebefore management actions are carried out. Another example is to requestthat the individual 114 press a button on the equipment to authorizemanagement connectivity.

In other implementations, the management capabilities may be used in atransparent mode. In the transparent mode, the individual 114 may notnecessarily be aware that the management system 102 is performingequipment management through the diagnostic device 136. In transparentmode, the diagnostic device 136 may establish the wireless diagnosticlink 140 automatically, e.g., when the diagnostic device 136 detects andconnects to a nearby piece of equipment. In that scenario, thediagnostic device 136 may regularly perform equipment maintenance (e.g.,firmware updates) whenever the diagnostic device 136 is within range ofa given piece of equipment.

The transparent mode connectivity and management activities may beinitiated and executed remotely, e.g., by a technician or automatedsystem associated with the management system 102. One example use caseis for residential broadband services. For example, assume that thenetwork operator detects a fault in fixed-line network (e.g., losesconnectivity with home gateway). Without contacting the subscriber, thenetwork operator may attempt to access the home gateway using a wirelessdiagnostic link management connection. If successful, the networkoperator isolates the fault and, if possible, restores service.Otherwise, the network operator may send an email/voicemail/textalerting the subscriber of the fixed-line network impairment andrecommending a corrective action.

Another example use case is the management of remote industrialequipment. For example, a technician, night watchman, robot, or otherentity may move through a facility that contains a number of short-rangewireless-enabled (Bluetooth, WiFi, etc.) pieces of equipment. As eachsuch unit comes within range, the diagnostic device 136 automaticallyconnects to it, thus allowing remote management systems to access theunit via the wireless diagnostic link and perform diagnostic and/ormanagement functions. As stated above, the person carrying the smartphone does not need to participate in the connectivity/managementactivities. One benefit is that in many instances of this scenario, theperson with the diagnostic device 136 does not require specializedtraining that a technician otherwise might need.

FIG. 6 shows additional examples of network configurations 602 and 650.In the configuration 602, the diagnostic device 604 includes adiagnostic application 606 extended to include any functionalityprovided by the management system 102. For example, the diagnosticdevice 604 may implement a voice recognition application 608 thatprovides voice driven troubleshooting of any DUT, executed directly onthe diagnostic device 604. Thus, the diagnostic application 606 mayprovide an expert system using any combination of voice, touch, andother input for troubleshooting in addition to, or instead or,troubleshooting performed over the wireless diagnostic link 140.

The configuration 602 also shows that any of the network interfacecomponents may be part of a consolidated device. In particular, theconfiguration 602 shows a home gateway 610. The home gateway 610includes the functionality associated with the network interface device118, the wireless router 120, and the network switch 122. The homegateway 610 may be a single device provided and managed by the networkoperator, for example. The home gateway 610 may vary widely infunctionality. For example, the home gateway 610 may or may not includethe wireless router 120 or the network switch 122. In addition, the homegateway 610 may include additional functionality, such as a DigitalVideo Recorder (DVR), Network Attached Storage (NAS), audio/videostreaming device, or other device.

FIG. 6 also shows another example configuration 650. In theconfiguration 650, the diagnostic device 136 obtains diagnosticinformation from a DUT, in this case the printer 126, over a wiredconnection 652. That is, in addition to using wireless connections suchas Bluetooth and NFC, the diagnostic device 136 may obtain diagnosticinformation over cabled (e.g., wired or optical) connections, such as aUSB, parallel, proprietary (e.g., a Lightning connector or iPhone™30-pin connector), Mobile High Definition, FireWire, or other type ofcabled connection.

The example configuration 650 also shows another connectivity option. Inparticular, the diagnostic device 136 may provide a tethered connection654 for any given DUT. In the example shown, the display 128 connects toa network via the tethered connection 654, with the diagnostic device136 then acting as an access point to the network. As a result, thediagnostic device may obtain diagnostic information from the display 128over the network link supported by the tethered connection 654. Thediagnostic device 136 may provide such a connection when, for example,the wireless router 120 is not available, e.g., is powered off, or ismalfunctioning, or is not present at all.

Note also that the diagnostic device 136 may also make connections tothe DUTs over different types of wireless analysis links, such as awireless network (e.g., WiFi or WiMax) link 656. That is, in addition toother types of wireless analysis links (e.g. Bluetooth and NFC), thediagnostic device 136 may attach to the wireless router 120 as a client,obtain a network address, and communicate over the network with theDUTs. As a result, the diagnostic device 136 may also obtain diagnosticdata by sending queries over the network in place at the servicelocation 104 to network connected devices at the service location 104.The example configuration 650 also shows a scenario in which a homegateway 658 includes the functionality of the network interface device118, wireless router 120, and network switch 122. However, as explainedabove, the network interface device 118, wireless router 120, andnetwork switch 122 may be separate devices instead, and additional,fewer, or different devices may be included in the home gateway 658.

In some implementations, the diagnostic device 136 may include a customhardware or software configuration that facilitates the diagnostictechniques discussed above. As one example, the diagnostic device 136may include a dedicated set of circuitry (e.g., a processor andfirmware) dedicated to establishing any of the links described above,obtaining diagnostic information, providing diagnostic instructions, andthe like. The dedicated circuitry may, for example, be separate andapart from the general purpose CPU and memory resources that thediagnostic device uses to run applications, make phone calls, handleWiFi or Bluetooth data connections, and the like. The management system102 may then attach to the diagnostic device 136 through the dedicatedcircuitry, independently of other tasks and connections that thediagnostic device 136 may be running or handling. In otherimplementations, the diagnostic device allocates diagnostic activitiesto a particular core among the multiple cores present in CPU. Thediagnostic device 136 may, for example, reserve a particular core fordiagnostic activities to ensure that the activities have the hardwaresupport needed to run at any given moment.

Discussed below are further aspects of the on-premises diagnostic,management, and self-installation (DMS) capabilities for customerpremises equipment (CPE).

FIG. 7 shows another example of a network diagram 700. Note that oneaspect of the DMS capabilities is the use of cellular channels forremote coordination of the DMS interactions with the CPE. For instance,the wireless diagnostic link 140 may be a cellular telephony link,including, as a few examples, a GSM, 2G, 3G, or 4G/LTE link. FIG. 7 alsoshows that test devices 702 may be used at the service location 104. Thetest devices 702 may be network analyzers, line testers, signal analysisand diagnostic devices, or any other device for testing any of the CPE.The test device 702 may itself include a cellular radio that supports acellular channel 704 for communication with the management system 102 orany other DMS system in the cloud of connected devices. In othersituations, the test device 702 may communicate over a wirelessconnection 708 (e.g., via Bluetooth) or over a wired connection 706(e.g., via USB) with another device (e.g., the diagnostic device 136)that provides the cellular channel. That is, the other device may sendand receive test results and other information over the wireless channel140 on behalf of the test device 702. More generally, the test device702 may communicate with the diagnostic device 136 over any type oftethered connection. Further, the test device 702 may perform anymanagement action other than test actions, including content management,device configuration, software management or other actions on targetdevices at the service location 104.

Regarding the diagnostic application 138, several implementation optionsare possible. As one example, a download/push mechanism may send thediagnostic application 138 to the diagnostic device 136, with or withoutnotification to the user of the diagnostic device 136. One mechanism forpreforming the push is an over-the-air update of the type that deliversnew firmware or operating system upgrades to cellular phones. Thediagnostic application 138 may be the particular data item pushed to thephone, or the diagnostic application 138 may be included as anapplication that is part of a larger data package (e.g., an operatingsystem upgrade) sent to the diagnostic device 136. The push may be froma remote location and may include a key, such as a decryption key, orany other access, authorization, or authentication key.

As another example, the diagnostic application may be pre-installed onthe diagnostic device 136. In that respect, part or all of thediagnostic application may be secured in the diagnostic device 136,e.g., located in a secure kernel, encrypted, protected by anauthorization or authentication mechanism, or otherwise sequestered inthe diagnostic device 136. The management system 102 (or any other DMSsystem) may then unlock the diagnostic application 138 for execution bysending, e.g., a decryption key, password, or other access information,without the need to push the diagnostic application 138 to thediagnostic device 136.

In other implementations, an authorization key for the diagnosticapplication 138 may be provided on or with the equipment for the CPEitself, e.g., as a PIN number on a router or LCD display. The diagnosticapplication 138 may execute in whole or in part in a secured executionenvironment within the diagnostic device 136. The secured executionenvironment may limit or prevent access to the diagnostic applicationand its data by other applications running on the diagnostic device 136.In other implementations, security may be accomplished by Near FieldCommunication (NFC) techniques. For instance, the diagnostic device 136may permit execution of the diagnostic application 138 when thediagnostic device 136 is in near field communication with a CPE, or withany other authorization or authentication device in the service location104.

As yet another example of provisioning the diagnostic application 138,the download, installation, and/or execution of the diagnosticapplication 138 may be responsive to a message, such as an email, SMSmessage, or other communication containing a link for the download,installation, or execution. Such an email may originate from themanagement system 102 or other remote location, for example. Thediagnostic application 138 may be available on an application storefrontfor free acquisition, or purchase, and download to the diagnostic device136. The application storefront may deliver the diagnostic application138 to the diagnostic device 136 through a data connection, e.g., an IPbased WiFi connection, through a 3G/4G/LTE data connection, or in otherways.

In some implementations, a network operator may verify execution rightsof the diagnostic application 138 against data in the SIM in thediagnostic device 136. For instance, the management system 102 mayverify that the current SIM card serial number matches a registered SIMcard number for the diagnostic device 136 prior to pushing thediagnostic application 138, prior to executing the diagnosticapplication 138, or prior to carrying out any DMS functionality.

The diagnostic device 136 may also implement authentication and securityfunctions with respect to the diagnostic application 138 and the CPE.The diagnostic application 138 may be configured for temporary access,e.g., for diagnostic purposes. The diagnostic device 136 may implement adiagnostic trusted zone, which may selectively permit the diagnosticapplication 138 to execute. Note that any technician management channelmay support the delivery and execution of the diagnostic application.That is, the management system 102 is just one source of the diagnosticapplication 138; the diagnostic application 138 may originate from otherdevices and systems, such as mobile technician devices operatinganywhere in the field.

Other aspects of security include digital signature authentication,e.g., of any of the gateways and the diagnostic device 136. Theauthentication may occur prior to installation or execution of thediagnostic application 138. The authentication may include SIM serialnumber or Mobile Device Management (MDM) factors or information. Thesystem may provide customer account privacy, e.g., through data hidingor obfuscation, regardless of where the customer account data is located(e.g., on the CPE or on the diagnostic device 136). Authentication orauthorization keys may be provisioned, protected, and linked to aparticular customer account, e.g., a customer of internet servicesupported through the network interface device 118 at the servicelocation 104. Any communication channel (e.g., NFC, cellular, USB, orWiFi channel) between the diagnostic device 136, CPE, management system102, or any other system may be secured, e.g., by encrypting the datasent over the channel. The secure communication channels may alsoinclude a secure channel between the SIMs on the diagnostic device 136and the management system 102, or any other DMS system in the cloud ofsystems in communication with the network device 136. The diagnosticdevice 136, CPEs, or DMS systems may detect and report unauthorized(e.g., malicious) attempts to access the diagnostic application 138 orthe CPEs at the service location 104, e.g., to the management system 102or any other DMS or MDM system through a secure or unsecured channel.

In some implementations, the diagnostic application 138 may obtain andrespond to customer profile information. The customer profileinformation may be stored in the management system 102 or any otherremote system in the cloud of devices with which the diagnostic device136 communicates. From the customer profile information, the diagnosticapplication may determine the device environment in place at the servicelocation 104, and the particular characteristics of any given CPE inquestion. The customer profile information (e.g., model number, firmwareversion, device identifiers, service package, street address, and thelike) may determine in whole or in part which DMS actions are executed,how they are executed, and what the results should be.

In some implementations, the diagnostic application 138 may perform CPEor service discovery, including querying CPEs for connected deviceinformation. In this manner, the diagnostic application 138 may buildsections of the customer profile and return the customer profile to themanagement system 102 for use in future DMS activities.

The system may implement application partitioning. For instance, thediagnostic device 136 may implement a thin client 710. The thin client710 may include, as one example, user interfaces and DMS functions thatinteract with the CPEs, while the network (e.g., the management system102) may implement comparatively more extensive or complex logic to,e.g., receive test data, perform DMS analysis, determine courses ofaction, send execution instructions to the diagnostic device 136, andotherwise monitor and execute DMS functions through the diagnosticdevice 136. In other implementations, the thin client 710 performs as aproxy layer to simply forward DMS data through the diagnostic device136. In this case, the CPE may execute the DMS functions and send theresults to the thin client 710. The thin client 710 relays the resultsto the management system 102, which performs the analysis on the resultsobtained through the thin client 710.

The DMS activities may be supported by parallel IP based sessions. Forinstance, the diagnostic device 136, management system 102, technician,or any combination thereof may execute a DMS session with more than oneCPE simultaneously, e.g., to send test data between CPEs and observe theresults. In another aspect, there may be several different paths orgateways to the management system 102 (or other external diagnostic orcontrol system) from the service location 104, any of which may be usedindividually or in parallel. The gateways may include an electricalnetwork interface (e.g., a smart-grid interface), the network interfacedevice 118, neighboring WiFi access point, femtocell, or a WAN into theservice location 104. Several examples are described below with respectto FIG. 8.

Further, the DMS actions may execute in parallel. There may be multiplemanagement systems 102, diagnostic devices 136 or diagnosticapplications 138 running in parallel. In that regard, multiple differentDMS agents may collaborate in parallel to perform the DMS actions, e.g.,a network configuration agent, a firmware upgrade agent, and a networktest packet generator agent running in parallel.

The diagnostic device 136 and the CPEs may execute any desired link andDMS protocols. The diagnostic device 136 and the CPEs may support thelink and DMS protocols with specific data structures that facilitate theDMS activities. Furthermore, when the diagnostic application 138executes, it may ascertain whether the diagnostic device 136 has thedrivers, interfaces, or other software components that may be needed tocommunicate with the CPE. If not, the diagnostic application 138 mayautomatically download and install such drivers, or direct the user to anetwork location where such drivers may be found and downloaded forinstallation. Note that the drivers may be obtained from the CPE itselfover any communication path in place between the diagnostic device 136and the CPE. Furthermore, the CPEs may themselves provide the diagnosticapplication 138 for execution by the diagnostic device 136. In thatrespect, the diagnostic device 136 need not obtain the diagnosticapplication 138 via a remote push operation, but may instead obtain thediagnostic application 138 locally from the CPE via any availablecommunication channel to the CPE.

In some implementations, the CPE may autonomously detect issues, andinitiate any DMS action, or initiate communication with the diagnosticdevice 136 or management system 102. That is, the CPE may initiate a DMSaction when it detects an issue that DMS actions can resolve.

Note that the diagnostic data sent or received over the wirelessdiagnostic link 140 may include both real time streaming and non-realtime cached data flows. The diagnostic device 136 may perform datagathering as a background task or in response to an event trigger (e.g.,loss of Internet connectivity).

Other types of DMS actions include monitoring latency and responsivelyadjusting any of the network devices (e.g., the router 120 or switch122) dynamically to reduce latency (or achieve a different quality goal)for a specific pathway. More generally, the diagnostic device or CPEsmay also predict behavioral issues in the network and perform proactiveadjustments to avoid the occurrence of the issues. The management system102 or any other device along the network path may monitor and assistwith cellular handovers for the diagnostic device 136, and may furtherimplement specific routing for specific application data streams. Forinstance, a video data stream may be routed over a high bandwidth, lowlatency path, while a camera audio sensor stream may be routed over alower bandwidth path.

The DMS analysis and actions are not limited to any particular device atthe service location 104 (e.g., the home gateway 610). The diagnosticapplication 138 may be designed for analysis of any CPE that may bepresent. Note also that the diagnostic application 138 may have adistributed architecture and may therefore have hardware and softwaremodules that reside in whole or in part at multiple locations or withinmultiple devices (e.g., within the diagnostic device 136, the homegateway 610 and any of its elements, the management system 102, or anyother location (e.g., in a cloud-connected device)).

Again, any of the DMS analysis may run autonomously, and if a problem isfound or anticipated, the analysis modules may search and locateinstructions for the related network elements and perform the DMS actionwithout user intervention (e.g., in the transparent mode explainedabove). The analysis modules may notify the user of the issue, and mayinterrupt the DMS action to ask for manual intervention. Further, thediagnostic application 138 may learn and update the DMS actions,including the particular DMS instructions and sequences. This may bebased upon a history log of which instructions and sequences worked andwhich did not work, on data from CPE manufacturers, on remote knowledgebases, or on other sources of information.

In some implementations, the diagnostic device 136 (e.g., a smartphone)may operate as an access point, e.g., and 802.11 access point. In thatrespect, the diagnostic device 136 may redirect diagnostic traffic toother devices, e.g., such as a television, laptop computer, or anothersmartphone, in order to act as a temporary gateway to route trafficaround non-functional equipment until that equipment is fixed.

FIG. 8 shows another example network diagram that illustrates additionalimplementation options. In FIG. 8, the cellular channel 802 (e.g., thewireless diagnostic link) is made to a local femtocell 804. A femtocellbasestation 806 (e.g., a low transmit power evolved Node B (eNB))generates the femtocell 804. The femtocell 804 may provide localcellular coverage for all or parts of a home or office, as examples. Thefemtocell basestation 806 may perform the functions of a cellularbasestation, for example, according to the 3GPP or 4G/LTE standards.

As just one example, the femtocell 804 may have footprint range fromabout 10s to 100s of meters, e.g., between 10 and 200 m. In aresidential environment, the femtocell 804 may support, e.g., 2 to 4active calls. The femtocell 804 increases the coverage area provided bymacrocells generated by full scale outdoor base stations, and mayimprove data throughput and voice quality. The femtocell 804 may furtherreduce uplink transmission power requirements from the UE 100, becausethe femtocell basestation 806 is much closer, and may therefore improvethe battery life of the diagnostic device 136.

FIG. 8 also shows an electrical network interface 808 present in theservice location 104. The electrical network interface 808 may include apower line network interface (e.g., an Ethernet over power lineinterface), a smart grid interface, or other interface that supportsdata transmission over the electrical network. The electrical networkmay connect back to the utility and to other locations, including themanagement system 102. Accordingly, the diagnostic device 136 mayexchange DMS information with other systems using any of a variety ofgateways that are available.

Another example of a gateway is an 802.11af White-Fi access point 810.The 802.11 of access point supports exchange of the DMS information inunused television spectrum. Additional examples of gateways throughwhich the diagnostic device 136 may exchange information include nearfield communications (NFC) interfaces, USB On The Go (USB OTG)interfaces, and phone line (e.g., RJ-11) interfaces (e.g., over amodem). The diagnostic device 136 may select a gateway based onreliability statistics, latency statistics, or other selection criteria.Further, as noted above, the communication pathways for the SDMinformation need not be real-time pathways. In that respect, thediagnostic device may obtain and save SDM information such as testresults, troubleshooting actions, test applications, or otherinformation on memory sticks, SIM cars, flash memory cards, and othermemory devices that may be transported to an analysis location forreview of the information, updating the information, and preparing theinformation for later return to the service location 104 where it may beapplied to CPE.

Note also that some or all of the DMS communications may be done in-bandin any selected communication channel. The in-band communications may bechosen according to the available bandwidth. As one example, the in-bandcommunications may be relatively slow compared to a dedicated channelfor the communications, but still sufficient for remote DMS purposes.

The DMS techniques described above were given in the example context ofa home or office. However, the DMS techniques, including gateway optionsand cellular channel communications, apply to other contexts as well.For instance, the DMS techniques apply in vehicles such as cars, ships,and planes, industrial settings (e.g., on the factory floor), and anyother private, public, or government location.

In many instances, the malfunctioning CPE is connected to other devicesin the network, e.g., the router 120 is in communication with the switch122. Each device in communication with the CPE may be directed (e.g., bythe diagnostic device 136), to load or save test data, to execute testson the CPE, to send instructions to the CPE (e.g., reboot or execute abuilt in self-test), and return results to the diagnostic device 136 orthrough the diagnostic device 136. Furthermore, the CPEs may be designedwith separate, isolated, or protected communication subsystems to reduceor eliminate the failure impacts of different communication systems inthe CPE on one another. For instance, the electrical interface, cellularinterface, and WiFi interfaces may be implemented as physically separatemodules to reduce the likelihood that failure of one would result infailure of another.

With the DMS capabilities, there may be multiple different types ofmanagement application functionality. The functionality may be presentin a single application, or may be distributed or partitioned acrossmultiple distinct applications. As examples, there may be functionalityspecific to addressing network optimization, network security,malfunctions, power saving configurations, high performance modeconfigurations, routine maintenance, testing, device setup,software/firmware installation, device programming, device upgrades, orother functionality applicable to a CPE. Within network optimization,for example, there may exist functionality for selecting and settingchannel assignments, adjusting output power levels, performinginterference detection, performing load balancing, performing latencyreduction, reducing power consumption, or other functions.

In other implementations, the CPE include built in self-test (BIST)functionality that may interact with the diagnostic device 136. Forexample, the BIST may communication test results to the diagnosticdevice 136 and receive configuration, repair, diagnosis, or other DMSdirections from the diagnostic device 136. The BIST functions mayimplement test patterns coordinated among one or more of the CPEs. Thetest patterns may test multiple different paths through the network thatconnects the CPEs, and test any desired functionality at any CPE alongthe path. Each instance of BIST may communicate test results back to themanagement system 102, or any other remote system located anywhere inthe cloud of network connected devices able to communicate with the BISTfunctions. In that respect, the DMS analysis need not be performed atthe management system 102, but may be performed in whole or in part inany system in the cloud of network devices able to communicate with theCPE.

Noted above was a transparent mode of operation for DMS activity. Otheraspects include execution of DMS activities through nearby devices. Forinstance, diagnostic devices in the vicinity (e.g., smartphones atneighboring locations) may be activated to troubleshoot CPEs at theservice location 104, or at the location where the diagnostic device isactually located. The neighboring diagnostic devices may attach to andcommunicate through network resources in the service location 104 to runDMS activities on the CPEs.

Regarding diagnostic devices in the vicinity, those devices and othersmay form a constellation of diagnostic devices, all or some or which mayexecute part of the DMS activities. Any of the diagnostic devices mayperform discovery, construction, and updating of device maps that thediagnostic devices may communicate back to the management system 102.The device maps may include any devices discovered by the diagnosticdevices, as well as location information (e.g., GPS or WiFi basedlocations) that geographically locates those discovered devices. Thatis, the diagnostic device 136 may send geographical device mappinginformation discovered by the diagnostic device 136 through the cellularcommunication channel to the management system 102. The device discoverymay happen autonomously, or a periodic basis, or responsive to userdirection and command. The information returned to the management system102 may also include environmental characteristics sensed by thediagnostic device 136. As just a few examples, the diagnostic device 136may return WiFi strength or quality measurements, cellular signalstrength or quality measurements, and access point identifiers (e.g.,SSIDs) to the management system 102, along with location information. Asa result, the management system 102 may build over time a geographic mapof devices, environmental characteristics, and other information sensedby any number of diagnostic devices 136 operating at any geographiclocations, including the service location 104.

Regarding diagnostic devices 136 in the service location 104, they mayactivate upon user command, or may activate on a more persistent basis.For instance, the diagnostic devices 136 may activate the diagnosticapplication 138 on a regular basis, e.g., on a periodic schedule orcontinuously running in the background. The DMS activities may thereforeoccur on a proactive basis, rather than a reactive basis in response toproblems with the CPEs.

As noted above, the techniques described in this application may performa full range of management actions on the entire range of equipment 116.As examples, the equipment 116 may include a home stereo, television,refrigerator, microwave, exercise machine, washer or dryer, or homesecurity system. As additional examples, the equipment may be a portablegaming device, audio/video controllers, or computer system, climatecontrol system (e.g., air conditioning and furnace), televisions,stereos, amplifiers, speakers, or any other type of electronic device.

The management actions are not limited to diagnosis, fault detection,and repair. Instead, the management actions may extend to contentmanagement, software management, device control, and beyond.Accordingly, in some implementations, the diagnostic device 136 performsfunctions other than diagnosis, troubleshooting and repair. Forinstance, the diagnostic device 136 may be part of a recognizedecosystem of devices within the service location, with the ecosystemdefined according to matching or common identifiers, e.g., queried,sent, or received over Bluetooth, to identify specific manufacturers,device types, or device functional characteristics. As a specificexample, the diagnostic device 136 may automatically recognize,establish communications with, and cooperate with devices at the servicelocation produced by a common manufacturer. Thus, for example, asmartphone diagnostic device may cooperate automatically with atelevision from a common manufacturer over any of the communicationchannels previously described (e.g., Bluetooth). The smartphone may thenshare pictures to the television, function as a remote control for thetelevision, set parental controls or other audio or video processingoptions, provide a channel for firmware upgrades for the television,launch diagnostic queries to the television, or otherwise interact withthe television.

The example above is a specific example of generalized tethering. Thatis, the diagnostic device 136 may establish, either manually orautomatically, links with any devices at the service location. In thatregard, the diagnostic device 136 provides a type of universalmanagement platform, e.g., for a family of products related by anyselected criteria (e.g., by manufacturer).

One result is that the diagnostic device 136 then provides part of thecommunication link into the service location, over a more secureconnection, the cellular connection (e.g., over 3G/4G/LTE), as comparedto a WiFi connection, for example. Therefore, a remote management system102 may more securely reach into the service location to perform anyselected management actions, automatically or with manual assistance, onthe devices in the service location, with the secure cellular connectionthrough the diagnostic device 136 made as an integral part of theoverall communication channel. In that respect, the cellular connectionmay act as the sole or primary channel, as opposed to a secondary orauxiliary channel.

Note also that a sensor system available on the diagnostic device 136may also contribute to device management. For instance, the diagnosticdevice 136 may capture images or video with a still camera or videocamera, capture or scan 1D, 2D, or other bar codes on the device beingmanaged, and capture or scan any other indicia (e.g., model names,serial numbers, and manufacturer names), and communicate the images, barcode data, or other indicia to the remote management system 102. Themanagement system 102 may index the indicia into a database of knownequipment, determine which equipment is being managed, and communicateaccordingly with the individual at the equipment location. For example,the management system 102 may communicate, e.g., through the smartphoneapplication, an identification of the device, and prompt the individualto confirm that the identified device is indeed the that the individualdesires to manage. Upon confirmation, the management system 102 may thenproceed with any specified management or troubleshooting action on thedevice.

Further, the management system 102 may accept the indicia as part of asecurity process. As one example, the indicia may serve asauthentication that the individual who is requesting management ortroubleshooting may actually do so. In one aspect, the indicia may serveto indicate that the individual is physically present with the device.That is, the individual is not an unauthorized party connecting througha remote WiFi or other network connection and who is attempting toimproperly modify device operation.

The methods, devices, and logic described above may be implemented inmany different ways in many different combinations of hardware, softwareor both hardware and software. For example, all or parts of the systemmay include circuitry in a controller, a microprocessor, or anapplication specific integrated circuit (ASIC), or may be implementedwith discrete logic or components, or a combination of other types ofanalog or digital circuitry, combined on a single integrated circuit ordistributed among multiple integrated circuits. All or part of the logicdescribed above may be implemented as instructions for execution by aprocessor, controller, or other processing device and may be stored in atangible or non-transitory machine-readable or computer-readable mediumsuch as flash memory, random access memory (RAM) or read only memory(ROM), erasable programmable read only memory (EPROM) or othermachine-readable medium such as a compact disc read only memory (CDROM),or magnetic or optical disk. Thus, a product, such as a computer programproduct, may include a storage medium and computer readable instructionsstored on the medium, which when executed in an endpoint, computersystem, or other device, cause the device to perform operationsaccording to any of the description above.

The DMS processing capability may be distributed among multiple systemcomponents, such as among multiple processors and memories, optionallyincluding multiple distributed processing systems. Parameters,databases, and other data structures may be separately stored andmanaged, may be incorporated into a single memory or database, may belogically and physically organized in many different ways, and mayimplemented in many ways, including data structures such as linkedlists, hash tables, or implicit storage mechanisms. Programs may beparts (e.g., subroutines) of a single program, separate programs,distributed across several memories and processors, or implemented inmany different ways, such as in a library, such as a shared library(e.g., a dynamic link library (DLL)). The DLL, for example, may storecode that performs any of the system processing described above.

What is claimed is:
 1. A management device comprising: a processor; acellular transceiver; and a memory in communication with the processorand the cellular transceiver, the memory comprising: controlinstructions that when executed by the processor cause the processor to:establish a cellular communication channel between a management systemand the management device, located at a service location; determinecustomer premises equipment (CPE) at the service location that shares anecosystem identifier with the management device; establish a localcommunication link between the management device and the CPE at theservice location; and managing the CPE at the service location by:receiving management instructions from the management system at themanagement device over the cellular communication channel; andresponding to the management instructions by sending responsivemanagement data over local communication link to the CPE.
 2. The deviceof claim 1, where the ecosystem identifier comprises a manufactureridentifier.
 3. The device of claim 1, where the ecosystem identifierspecifies a device functional characteristic.
 4. The device of claim 1,where the management instructions comprise content managementinstructions.
 5. The device of claim 1, where the managementinstructions comprise diagnostic queries for the CPE.
 6. The device ofclaim 1, where the control instructions are configured to manage the CPEwithout notification on a user interface of the management device.
 7. Amethod comprising: establishing a cellular communication channel betweena management system and a management device located at a servicelocation; establishing a tethered connection between the managementdevice and a separate tethered device also located at the servicelocation; and managing customer premises equipment (CPE) at the servicelocation by: receiving management instructions from the managementsystem at the management device over the cellular communication channel;responding to the management instructions by sending responsivemanagement data over the tethered connection to the tethered device;receiving management response data from the CPE over the tetheredconnection from the tethered device at the management device; andreturning the management response data to the management system over thecellular communication channel.
 8. The method of claim 7, furthercomprising executing a management application on the management deviceto receive the management instructions.
 9. The method of claim 7,further comprising: establishing the cellular communication channelthrough a cellular radio in the management device.
 10. The method ofclaim 8, where: the management instructions comprise test instructionsfor the CPE at the service location.
 11. The method of claim 7, where:the management instructions comprise device configuration instructionsfor the CPE at the service location.
 12. The method of claim 7, furthercomprising: pushing a management application to the management devicefrom the management system for use in managing the CPE.
 13. The methodof claim 7, further comprising: delivering a management application linkto the management device; and executing the management application onthe management device responsive to activation of the managementapplication link.
 14. A management device comprising: a processor; acellular transceiver; and a memory in communication with the processorand the cellular transceiver, the memory comprising: controlinstructions that when executed by the processor cause the processor to:establish a cellular communication channel between a management systemand the management device, located at a service location; establish atethered connection between the management device and a separatetethered device also located at the service location; and managingcustomer premises equipment (CPE) at the service location by: receivingmanagement instructions from the management system at the managementdevice over the cellular communication channel; responding to themanagement instructions by sending responsive management data over thetethered connection to the tethered device; receiving managementresponse data over the tethered connection from the tethered device atthe management device; and returning the management response data to themanagement system over the cellular communication channel.
 15. Thedevice of claim 14, where: the management instructions comprise testinstructions for the CPE at the service location.
 16. The device ofclaim 14, where: the management instructions comprise deviceconfiguration instructions for the CPE at the service location.
 17. Thedevice of claim 14, where: the control instructions are configured tomanage the CPE without notification on a user interface of themanagement device.
 18. The device of claim 14, where: the controlinstructions are configured to manage the CPE automatically and withoutinput from a user interface of the management device.
 19. The device ofclaim 14, where: the control instructions are configured to establishthe cellular communication channel between the management system and themanagement device automatically and without input from a user interfaceof the management device.
 20. The device of claim 14, where: the controlinstructions are further configured to: receive a message comprising anapplication link to a diagnostic application from the management system,the message regarding management of the CPE; respond to selection of theapplication link by downloading and executing the diagnosticapplication; and managing the CPE through the diagnostic application.